Techniques for encoding beacon signals in wireless power delivery environments

ABSTRACT

Embodiments of the present disclosure describe techniques for encoding beacon signals in wireless power delivery environments. More specifically, techniques are disclosed for encoding beacon signals to isolate client devices for wireless power delivery in wireless power delivery environments. The beacon signals can be encoded or modulated with a transmission code that is provided to selected clients in the wireless power delivery environment. In this manner, beacon signals from the select clients can be identified and the corresponding client devices isolated for wireless power delivery. In some embodiments, the transmission code can be a pseudorandom sequence that is used by the wireless power delivery clients to encode transmitted beacon signals.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to and benefit from U.S. ProvisionalPatent Application Ser. No. 62/086,481 titled “TECHNIQUES FORIDENTIFYING CLIENTS AND CHARGERS IN WIRELESS POWER ENVIRONMENTS” filedon Dec. 2, 2014, which is expressly incorporated by reference herein.

BACKGROUND

Signal transmission between wireless chargers and client devices in awireless power delivery environment can be challenging. For example,client devices can periodically transmit beacon signals or othersignaling to a wireless charger so that the wireless charger canspecifically direct wireless power to the client device. Unfortunately,when there are multiple client devices in the same environment, thewireless charger may inadvertently direct power to an unauthorized orincorrect wireless device. That is, the wireless charger mayinadvertently lock onto an unauthorized transmission source (e.g.,another wireless device or other transmitter) that is transmitting atthe same frequency as the wireless device resulting in wireless powerbeing directed to the unauthorized transmission source rather than theintended wireless device.

Accordingly, a need exists for technology that overcomes the problemdemonstrated above, as well as one that provides additional benefits.The examples provided herein of some prior or related systems and theirassociated limitations are intended to be illustrative and notexclusive. Other limitations of existing or prior systems will becomeapparent to those of skill in the art upon reading the followingDetailed Description.

BRIEF DESCRIPTION OF THE DRAWINGS

One or more embodiments of the present invention are illustrated by wayof example and not limitation in the figures of the accompanyingdrawings, in which like references indicate similar elements.

FIG. 1 depicts a block diagram illustrating an example wireless powerdelivery environment depicting isolated wireless power delivery from oneor more wireless chargers to various wireless devices within thewireless power delivery environment.

FIG. 2 depicts a sequence diagram illustrating example operationsbetween a wireless charger and a wireless receiver device for commencingisolated wireless power delivery in accordance with some embodiments.

FIG. 3 depicts a block diagram illustrating example components of awireless power transmitter (charger or wireless power delivery system)in accordance with some embodiments.

FIG. 4 depicts a block diagram illustrating example components of awireless power receiver (client) in accordance with some embodiments.

FIGS. 5A-5C depict a flow diagram illustrating an example process ofencoding beacon signals for isolating a power receiver client forwireless power delivery in accordance with some embodiments.

FIGS. 6 and 7 are signaling diagrams illustrating example transmissionschedules, according to some embodiments.

FIG. 8 depicts a block diagram illustrating example components of arepresentative mobile device or tablet computer with a wireless powerreceiver or client in the form of a mobile (or smart) phone or tabletcomputer device, according to some embodiments.

FIG. 9 depicts a diagrammatic representation of a machine, in theexample form, of a computer system within which a set of instructions,for causing the machine to perform any one or more of the methodologiesdiscussed herein, may be executed.

DETAILED DESCRIPTION

The following description and drawings are illustrative and are not tobe construed as limiting. Numerous specific details are described toprovide a thorough understanding of the disclosure. However, in certaininstances, well-known or conventional details are not described in orderto avoid obscuring the description. References to one or an embodimentin the present disclosure can be, but not necessarily are, references tothe same embodiment; and, such references mean at least one of theembodiments.

Reference in this specification to “one embodiment” or “an embodiment”means that a particular feature, structure, or characteristic describedin connection with the embodiment is included in at least one embodimentof the disclosure. The appearances of the phrase “in one embodiment” invarious places in the specification are not necessarily all referring tothe same embodiment, nor are separate or alternative embodimentsmutually exclusive of other embodiments. Moreover, various features aredescribed which may be exhibited by some embodiments and not by others.Similarly, various requirements are described which may be requirementsfor some embodiments but no other embodiments.

The terms used in this specification generally have their ordinarymeanings in the art, within the context of the disclosure, and in thespecific context where each term is used. Certain terms that are used todescribe the disclosure are discussed below, or elsewhere in thespecification, to provide additional guidance to the practitionerregarding the description of the disclosure. For convenience, certainterms may be highlighted, for example using italics and/or quotationmarks. The use of highlighting has no influence on the scope and meaningof a term; the scope and meaning of a term is the same, in the samecontext, whether or not it is highlighted. It will be appreciated thatsame thing can be said in more than one way.

Consequently, alternative language and synonyms may be used for any oneor more of the terms discussed herein, nor is any special significanceto be placed upon whether or not a term is elaborated or discussedherein. Synonyms for certain terms are provided. A recital of one ormore synonyms does not exclude the use of other synonyms. The use ofexamples anywhere in this specification, including examples of any termsdiscussed herein, is illustrative only, and is not intended to furtherlimit the scope and meaning of the disclosure or of any exemplifiedterm. Likewise, the disclosure is not limited to various embodimentsgiven in this specification.

Without intent to further limit the scope of the disclosure, examples ofinstruments, apparatus, methods and their related results according tothe embodiments of the present disclosure are given below. Note thattitles or subtitles may be used in the examples for convenience of areader, which in no way should limit the scope of the disclosure. Unlessotherwise defined, all technical and scientific terms used herein havethe same meaning as commonly understood by one of ordinary skill in theart to which this disclosure pertains. In the case of conflict, thepresent document, including definitions, will control.

Embodiments of the present disclosure describe techniques for encodingbeacon signals in wireless power delivery environments. Morespecifically, techniques are disclosed for encoding beacon signals toisolate client devices for wireless power delivery in wireless powerdelivery environments. The beacon signals can be encoded or modulatedwith a transmission code that is provided to selected clients in thewireless power delivery environment. In this manner, beacon signals fromthe select clients can be identified and the corresponding clientdevices isolated for wireless power delivery. In some embodiments, thetransmission code can be a pseudorandom sequence that is used by thewireless power delivery clients to encode transmitted beacon signals.

In some embodiments, the same transmission code is used for all clients(transmission code unique to charger). In other embodiments, a differenttransmission code is provided to each client or communication path. Asdiscussed in more detail with reference to FIG. 7, differenttransmission codes for each client can facilitate simultaneous or nearsimultaneous transmission of beacon signaling by the clients in thewireless power delivery environment further ensuring that onlyauthorized (selected) clients are “locked” by the wireless powerdelivery system.

In some embodiments, the techniques illustrated herein achieve, amongother things, accurate identification and tracking of clients bychargers (e.g., “locking”) in wireless power delivery environments. Theaccurate identification prevents locking onto unauthorized sources.

By way of example and not limitation, the beacon encoding techniquesdescribed herein can be used in various industrial, military, counterterrorism applications, conservation of energy, quality of environmentand medical applications, etc. that can require having more than onecharger to deliver power and identify many authorized wireless devicesin the same environment without interference.

FIG. 1 is a diagram illustrating an example wireless power deliveryenvironment 100 depicting isolated wireless power delivery from one ormore wireless chargers 101 to various wireless devices 102 within thewireless power delivery environment 100. More specifically, FIG. 1illustrates an example wireless power delivery environment 100 in whichwireless power and/or data can be delivered to available wirelessdevices 102.1-102.n having one or more power receiver clients103.1-103.n (also referred to herein as “wireless power receivers” or“wireless power clients”). The wireless power receivers are configuredto receive isolated wireless power from one or more wireless chargers101.

As shown in the example of FIG. 1, the wireless devices 102.1-102.n aremobile phone devices 102.2 and 102.n, respectively, and a wireless gamecontroller 102.1, although the wireless devices 102.1-102.n can be any(smart or dumb) wireless device or system that needs power and iscapable of receiving wireless power via one or more integrated powerreceiver clients 103.1-103.n. As discussed herein, the one or moreintegrated power receiver clients or “wireless power receivers” receiveand process power from one or more transmitters/chargers 101.a-101.n andprovide the power to the wireless devices 102.1-102.n for operationthereof.

Each charger 101 (also referred to herein as a “transmitter”, “array ofantennas” or “antenna array system”) can include multiple antennas 104,e.g., an antenna array including hundreds or thousands of antennas,which are capable of delivering wireless power to wireless devices 102.In some embodiments, the antennas are adaptively-phased radio frequencyantennas. The charger 101 is capable of determining the appropriatephases to deliver a coherent power transmission signal to the powerreceiver clients 103. The array is configured to emit a signal (e.g.,continuous wave or pulsed power transmission signal) from multipleantennas at a specific phase relative to each other. It is appreciatedthat use of the term “array” does not necessarily limit the antennaarray to any specific array structure. That is, the antenna array doesnot need to be structured in a specific “array” form or geometry.Furthermore, as used herein he term “array” or “array system” may beused include related and peripheral circuitry for signal generation,reception and transmission, such as radios, digital logic and modems. Insome embodiments, the charger 101 can have an embedded Wi-Fi hub.

The wireless devices 102 can include one or more receive power clients103. As illustrated in the example of FIG. 1, power delivery antennas104 a and data communication antennas 104 b are shown. The powerdelivery antennas 104 a are configured to provide delivery of wirelessradio frequency power in the wireless power delivery environment. Thedata communication antennas are configured to send data communicationsto and receive data communications from the power receiver clients103.1-103 and/or the wireless devices 102.1-102.n. In some embodiments,the data communication antennas can communicate via Bluetooth, Wi-Fi,ZigBee, etc.

Each power receiver client 103.1-103.n includes one or more antennas(not shown) for receiving signals from the chargers 101. Likewise, eachcharger 101.a-101.n includes an antenna array having one or moreantennas and/or sets of antennas capable of emitting continuous wavesignals at specific phases relative to each other. As discussed above,each array is capable of determining the appropriate phases fordelivering coherent signals to the power receiver clients 102.1-102.n.For example, coherent signals can be determined by computing the complexconjugate of a received beacon signal at each antenna of the array suchthat the coherent signal is properly phased for the particular powerreceiver client that transmitted the beacon signal.

Although not illustrated, each component of the environment, e.g.,wireless power receiver, charger, etc., can include control andsynchronization mechanisms, e.g., a data communication synchronizationmodule. The chargers 101.a-101.n can be connected to a power source suchas, for example, a power outlet or source connecting the chargers to astandard or primary alternating current (AC) power supply in a building.Alternatively or additionally, one or more of the chargers 101.a-101.ncan be powered by a battery or via other mechanisms.

In some embodiments, the power receiver clients 102.1-102.n and/or thechargers 101.a-101.n utilize reflective objects 106 such as, forexample, walls or other RF reflective obstructions within range totransmit beacon signals and/or receive wireless power and/or data withinthe wireless power delivery environment. The reflective objects 106 canbe utilized for multi-directional signal communication regardless ofwhether a blocking object is in the line of sight between the chargerand the power receiver client.

As described herein, each wireless device 102.1-102.n can be any systemand/or device, and/or any combination of devices/systems that canestablish a connection with another device, a server and/or othersystems within the example environment 100. In some embodiments, thewireless devices 102.1-102.n include displays or other outputfunctionalities to present data to a user and/or input functionalitiesto receive data from the user. By way of example, a wireless device 102can be, but is not limited to, a video game controller, a serverdesktop, a desktop computer, a computer cluster, a mobile computingdevice such as a notebook, a laptop computer, a handheld computer, amobile phone, a smart phone, a PDA, a Blackberry device, a Treo, and/oran iPhone, etc. The wireless device 102 can also be any wearable devicesuch as watches, necklaces, rings or even devices embedded on or withinthe customer. Other examples of a wireless device 102 include, but arenot limited to, safety sensors (e.g., fire or carbon monoxide), electrictoothbrushes, electronic door lock/handles, electric light switchcontroller, electric shavers, etc.

Although not illustrated in the example of FIG. 1, the charger 101 andthe power receiver clients 103.1-103.n can each include a datacommunication module for communication via a data channel. Alternativelyor additionally, the power receiver clients 103.1-103.n can direct thewireless devices 102.1-102.n to communicate with the charger viaexisting data communications modules. Additionally, in some embodimentsthe beacon signal, which is primarily referred to herein as a continuouswaveform, can alternatively or additionally take the form of a modulatedsignal.

FIG. 2 is a sequence diagram 200 illustrating example operations betweena wireless charger 101 and a power receiver client 103 for commencingisolated wireless power delivery, according to an embodiment. Initially,communication is established between the charger 101 and the powerreceiver client 103. The charger 101 subsequently sends beacon scheduleinformation and a transmission code to the power receiver client 103 tofacilitate encoding of the beacon signal by the power receiver client103 for subsequent isolated wireless power delivery by the charger. Thecharger 101 can also send power transmission scheduling information sothat the power receiver client 103 knows when to expect wireless powerfrom the charger. As discussed herein, the power receiver client 103generates an encoded beacon signal using the transmission code andbroadcasts the encoded beacon during a beacon transmission assignmentindicated by the beacon schedule information, e.g., BBS cycle.

As shown, the charger 101 receives the beacon from the power receiverclient 103 and decodes the encoded beacon signal using the transmissioncode provided to the client 103 to ensure that the client 103 is anauthorized or selected client. The charger 101 also detects the phase(or direction) at which the beacon signal is received and, once thecharger determines that the client is authorized, delivers wirelesspower and/or data to the power receiver client 103 based the phase (ordirection) of the received beacon. In some embodiments, the charger 101can determine the complex conjugate of the phase and use the complexconjugate to deliver and/or otherwise direct wireless power to the powerreceiver client 103 in the same direction (or phase) in which the beaconsignal was received from the power receiver client 103.

In some embodiments, the charger 101 includes many antennas; one or moreof which are used to deliver power to the power receiver client 103. Thecharger 101 can detect phases at which the beacon signals are receivedat each antenna. The large number of antennas may result in differentcoded beacon signals being received at each antenna of the charger 101.The charger may then determine the complex conjugate of the beaconsignals received at each antenna. Using the complex conjugates, one ormore antenna may emit a signal that takes into account the effects ofthe large number of antennas in the charger 101. In other words, thecharger 101 emits a signal from one or more antennas in such a way as tocreate an aggregate signal from the one or more of the antennas thatapproximately recreates the waveform of the beacon in the oppositedirection.

As discussed herein, wireless power can be delivered in power cyclesdefined by power schedule information. A more detailed example of thesignaling required to commence wireless power delivery is described nowwith reference to FIG. 3.

FIG. 3 is a block diagram illustrating example components of a wirelesscharger 300, in accordance with an embodiment. As illustrated in theexample of FIG. 3, the wireless charger 300 includes a master buscontroller (MBC) board and multiple mezzanine boards that collectivelycomprise the antenna array. The MBC includes control logic 310, anexternal power interface (I/F) 320, a communication block 330, and proxy340. The mezzanine (or antenna array boards 350) each include multipleantennas 360 a-360 n. Some or all of the components can be omitted insome embodiments. Additional components are also possible.

The control logic 310 is configured to provide control and intelligenceto the array components. The control logic 310 may comprise one or moreprocessors, FPGAs, memory units, etc., and direct and control thevarious data and power communications. The communication block 330 candirect data communications on a data carrier frequency, such as the basesignal clock for clock synchronization. The data communications can beBluetooth, Wi-Fi, ZigBee, etc. Likewise, the proxy 340 can communicatewith clients via data communications as discussed herein. The datacommunications can be Bluetooth, Wi-Fi, ZigBee, etc. The external powerinterface 320 is configured to receive external power and provide thepower to various components. In some embodiments, the external powerinterface 320 may be configured to receive a standard external 24 Voltpower supply. Alternative configurations are also possible.

An example of a system power cycle is now described. In this example,the master bus controller (MBC), which controls the charger array, firstreceives power from a power source and is activated. The MBC thenactivates the proxy antenna elements on the charger array and the proxyantenna elements enter a default “discovery” mode to identify availablewireless receiver clients within range of the charger array. When aclient is found, the antenna elements on the charger array power on,enumerate, and (optionally) calibrate.

Next, the MBC generates beacon transmission scheduling information andpower transmission scheduling information during a scheduling process.The scheduling process includes selection of power receiver clients. Forexample, the MBC can select power receiver clients for powertransmission and generate a Beacon Beat Schedule (BBS) cycle and a PowerSchedule (PS) for the selected wireless power receiver clients. Agraphical signaling representation of an example BBS and PS is shown anddiscussed in greater detail with reference to FIGS. 6 and 7. Asdiscussed herein, the power receiver clients can be selected based ontheir corresponding properties and/or requirements.

In some embodiments, the MBC can also identify and/or otherwise selectavailable clients that will have their status queried in the ClientQuery Table (CQT). Clients that are placed in the CQT are those on“standby”, e.g., not receiving a charge. The BBS and PS are calculatedbased on vital information about the clients such as, for example,battery status, current activity/usage, how much longer the client hasuntil it runs out of power, priority in terms of usage, etc.

The Proxy AE broadcasts the BBS to all clients. As discussed herein, theBBS indicates when each client should send a beacon. Likewise the PSindicates when and to which clients the array should send power to. Eachclient starts broadcasting its beacon and receiving power from the arrayper the BBS and PS. The Proxy can concurrently query the Client QueryTable to check the status of other available clients. A client can onlyexist in the BBS or the CQT (e.g., waitlist), but not in both. In someembodiments, a limited number of clients can be served on the BBS and PS(e.g., 32). Likewise, the CQT may also be limited to a number of clients(e.g., 32). Thus, for example, if more than 64 clients are within rangeof the charger, some of those clients would not be active in either theBBS or CQT. The information collected in the previous step continuouslyand/or periodically updates the BBS cycle and/or the PS.

FIG. 4 is a block diagram illustrating example components of a wirelesspower receiver (client), in accordance with some embodiments. Asillustrated in the example of FIG. 4, the receiver 400 includes controllogic 410, battery 420, communication block 430 and associated antenna470, power meter 440, rectifier 450, a combiner 455, beacon signalgenerator 460, beacon coding unit 462 and an associated antenna 480, andswitch 465 connecting the rectifier 450 or the beacon signal generator460 to one or more associated antennas 490 a-n. Some or all of thecomponents can be omitted in some embodiments. For example, in someembodiments, the wireless power receiver client does not include its ownantennas but instead utilizes and/or otherwise shares one or moreantennas (e.g., Wi-Fi antenna) of the wireless device in which thewireless power receiver is embedded. Additional components are alsopossible.

A combiner 455 receives and combines the received power transmissionsignals from the power transmitter in the event that the receiver 400has more than one antenna. The combiner can be any combiner or dividercircuit that is configured to achieve isolation between the output portswhile maintaining a matched condition. For example, the combiner 455 canbe a Wilkinson Power Divider circuit. The rectifier 450 receives thecombined power transmission signal from the combiner 455, if present,which is fed through the power meter 440 to the battery 420 forcharging. The power meter 440 measures the received power signalstrength and provides the control logic 410 with this measurement.

The control logic 410 also may receive the battery power level from thebattery 420 itself. The control logic 410 may also transmit/receive viathe communication block 430 a data signal on a data carrier frequency,such as the base signal clock for clock synchronization. The beaconsignal generator 460 generates the beacon signal, or calibration signal,transmits the beacon signal using either the antenna 480 or 490 afterthe beacon signal is encoded.

It may be noted that, although the battery 420 is shown for as chargedby and providing power to the receiver 400, the receiver may alsoreceive its power directly from the rectifier 450. This may be inaddition to the rectifier 450 providing charging current to the battery420, or in lieu of providing charging. Also, it may be noted that theuse of multiple antennas is one example of implementation and thestructure may be reduced to one shared antenna.

In some embodiments, a client identifier (ID) module 415 stores a clientID that can uniquely identify the power receiver client in a wirelesspower delivery environment. For example, the ID can be transmitted toone or more chargers when communication are established. In someembodiments, power receiver clients may also be able to receive andidentify other power receiver clients in a wireless power deliveryenvironment based on the client ID.

An optional motion sensor 495 can detect motion and signal the controllogic 410 to act accordingly. For example, when a device is receivingpower at high frequencies, e.g., above 500 MHz, its location may becomea hotspot of (incoming) radiation. Thus, when the device is on a person,e.g., embedded in a mobile device, the level of radiation may exceedacceptable radiation levels set by the Federal Communications Commission(FCC) or other medical/industrial authorities. To avoid any potentialradiation issue, the device may integrate motion detection mechanismssuch as accelerometers or equivalent mechanisms. Once the device detectsthat it is in motion, it may be assumed that it is being handled by auser, and would trigger a signal to the array either to stoptransmitting power to it, or to lower the received power to anacceptable fraction of the power. In cases where the device is used in amoving environment like a car, train or plane, the power might only betransmitted intermittently or at a reduced level unless the device isclose to losing all available power.

FIGS. 5A-5C depict flow diagrams illustrating an example process 500 forencoding beacon signals to isolate a power receiver client for wirelesspower delivery in accordance with some embodiments. A wireless devicehaving an embedded wireless power receiver client and a wireless powerdelivery system can, among other functions, perform the correspondingsteps of example process 500. The wireless power delivery system can bea wireless charger or components of a wireless charger, e.g., a wirelesscharger 101 of FIG. 1 or wireless charger 300 of FIG. 3, and/or aprocessing system, e.g., control logic 310 of FIG. 3. Likewise thewireless power receiver client can be wireless power receiver 103 ofFIG. 1, wireless power receiver client 400 of FIG. 4 or variouscomponents of a wireless power receiver client. Alternativeconfigurations are also possible.

To begin, at steps 510A and 510B, communication is established betweenthe wireless power receiver client and the wireless power deliverysystem. As discussed above, in some embodiments, the wireless powerdelivery system can enter a default “discovery” mode to identifyavailable wireless power receiver clients within range of the charger.When a client is found, the antenna elements on the charger array poweron, enumerate, and (optionally) calibrate. The communication with thewireless power receiver client can be over one or more antennas of themultiple antennas of the wireless power delivery system. In someembodiments, a single antenna is used to establish communications withwireless power receiver clients.

Once communication is established between the wireless power receiverclient and the wireless power delivery system, at step 512, the wirelesspower receiver client gathers and sends client-specific information tothe wireless power delivery system. As discussed above, theclient-specific information can include various properties and/orrequirements corresponding to the power receiver client or wirelessdevice in which the power receiver client is embedded. For example, theclient-specific information can include, but is not limited to, batterylevel of the wireless device in which the power receiver client isembedded, battery level of the power receiver client, battery usageinformation, temperature information, etc. As discussed herein, thetemperature information can include current temperature of the wirelessdevice or wireless power receiver or, ambient temperature of thewireless device or wireless power receiver.

At step 514, the wireless power delivery system receives theclient-specific information for the available wireless power receiverclients within range of the wireless power delivery system, e.g.,charger. Once the client-specific information is received, the wirelesspower delivery system, at step 516, determines and/or otherwiseidentifies additional information about the wireless power receiverclients. The additional information can be any information that thewireless power delivery system can glean or otherwise obtain from theclient. For example, the wireless power delivery system can determinethe distance or range between the client and the wireless power deliverysystem based on the received signal strength indication (RSSI). The RSSIcan be measured by the wireless power delivery system or measured andreceived from the client. The RSSI can also be an indicator ofefficiency. Other distance determination methodologies are alsopossible. Furthermore, it is appreciated that the additional informationcan comprise other information obtained by the wireless power deliverysystem.

At step 518, the wireless power delivery system generates transmissionscheduling information based on various predetermined priorities whichcan include the client-specific information and other informationgleaned by the wireless power delivery system, e.g., distance to thewireless power delivery system. As discussed above, generating thetransmission scheduling information can include: selecting a set (orsubset) of the available wireless power receiver clients within range ofthe wireless power delivery system and generating beacon transmissionscheduling information and power delivery scheduling information for theselected set of wireless power receiver clients. The beacon transmissionscheduling information can comprise a BBS cycle. The power deliveryscheduling information can comprise a power schedule (PS) for theselected wireless power receiver clients.

At step 520, the wireless power delivery system identifies and/orotherwise selects transmission code information. In some embodiments,the transmission code can comprise a pseudo-random sequence that is usedby clients to modulate beacon signals so that the wireless powerdelivery system can identify and/or otherwise isolate the client devicefor wireless power delivery. As discussed herein, a unique transmissioncode can be selected for each wireless device that is scheduled toreceive wireless power. Alternatively, a transmission code can beselected that is unique to a particular wireless power delivery system.Once selected, at step 522, the wireless power delivery system sends thetransmission scheduling information and the transmission code to thewireless power receiver client.

At step 524, the wireless power receiver client receives thetransmission scheduling information and the transmission code and, atstep 526, encodes a beacon signal based on the transmission code. It isappreciated that various modulation schemes can be used to encode thebeacon signal such as, but not limited to, frequency-shift keying,amplitude-shift keying, phase-shift keying, quadrature modulationschemes, m-ary modulation schemes, etc. For purposes of illustration,the examples described herein primarily discuss encoding of a beaconsignal using phase-shift keying or other phase modulation techniques.Phase-shift keying is a digital modulation scheme that conveys data bychanging, or modulating, the phase of a reference signal (the carrierwave). In some embodiments, the beacon signal is changed or modulatedbased on the pseudorandom sequence (or transmission code).

For example, the sequence can comprise a binary number in which every“1” in the sequence corresponds to a certain predetermined degree ofphase shift. The predetermined degree of phase shift can be defined bythe wireless power delivery system and communicated to the wirelesspower receiver client during initial communications. Alternatively, thepredetermined degree of phase shift can be pre-defined in other waysand/or hardcoded in the device or embedded power receiver client.Likewise, in this example, every “0” in the sequence can correspond to azero degree phase shift in that particular section of the signal. Forexample, if the pseudorandom sequence is “101010110 . . . 1”, thewireless power receiver client can phase shift the beacon it broadcastsin a manner that matches that sequence. This allows the charger toidentify the client and proceed with the wireless power delivery asillustrated in the sections below.

In some embodiments, encoding the beacon signal comprises phasemodulating or phase shifting the beacon signal. Phase modulation is amodulation pattern that encodes information as variations in theinstantaneous phase of a carrier wave. For example, after receiving thepseudorandom sequence sent by the charger, the selected wirelessreceiver can phase-modulate a beacon signal based on the pseudorandomsequence.

By way of example, if the pseudo-random sequence (called the modulatingor message signal) is represented by m(t) and the carrier onto which thesignal is to be modulated is c(t)=A_(c) sin(ω_(c)t+φ_(c)). then themodulated signal can be represented as y(t)=A_(c)sin(ω_(c)t+m(t)+φ_(c)).

As discussed above, various modulation or coding schemes can be used toencode the beacon signals including combinations or variations thereof.

At step 528 the wireless power receiver client processes thetransmission scheduling information to identify a beacon transmissionassignment assigned to the wireless power receiver client and, atdecision step 532, the wireless power receiver client monitors for theassigned beacon cycle. If the beacon cycle is detected, at step 534, thewireless power receiver client sends the encoded beacon signal to thewireless power delivery system and, at decision step 538, the wirelesspower receiver client monitors for the assigned power cycle. If theclient device determines that its power cycle is approaching then itwill listen or otherwise wait to receive power during the cycle. In someembodiments, the client device can preserve power by only “listening”during its prescribed power cycle.

At step 540, the wireless power delivery system receives the encodedbeacon signal and, at step 542, decodes the beacon signal. For example,if the beacon signal is phase modulated, then the beacon signal isdemodulated at step 542. At step 544, the wireless power delivery systemmeasures the phases of the received beacon signal. For example,

At step 546, the wireless power delivery system determines the relativelocation of the power receiver client within the wireless power deliveryenvironment based, at least in part, on the measured phases. Asdiscussed herein, the power receiver clients can be tracked through thewireless power delivery environment based on beacon signals which areperiodically transmitted based on the BBS. Authorized clients embedtransmission codes into their beacons so that the wireless powerdelivery system does not confuse them with unauthorized devices, e.g., arogue device transmitting at the same frequency as an authorized clientdevice but either not currently selected for wireless power delivery oran interference source, e.g., another charger, Wi-Fi router, etc.Additionally, in some embodiments, if the authorized client embeds acode onto its beacon, then the wireless power delivery system canidentify the location(s) of the interference sources, e.g., unauthorizedtransmitters, and avoids locking onto those interference sources. Insome embodiments, the charger can track the locations of theinterference sources to ensure that they are not confused withauthorized transmitters.

At decision step 548, the wireless power delivery system determines ifthe power cycle for the particular wireless power receiver client isactive and, if so, at step 550 sends a coherent power signal to thewireless power delivery client during the power cycle as describedherein. Lastly, at step 552, the wireless power receiver client receivesthe power signal and, at step 554 processes the power to charge one ormore batteries as described herein.

FIG. 6 is a signaling diagram illustrating example transmission schedule600 for multiple power receiver clients #1-N and a wireless powerdelivery system in a wireless power delivery environment, according tosome embodiment. The example transmission schedule 600 involves use of asingle pseudorandom sequence. Although a single charger is shown in theexample of FIG. 6, it is appreciated that the wireless power deliveryenvironment can include multiple wireless power receiver clients.

As illustrated in the example of FIG. 6, the power delivery schedule caninclude an indication of the power delivery shares (or cycles) assignedto each of the selected clients. As described herein, the chargerdetects the phase modulated beacon based on the pre-identifiedpseudorandom sequence communicated to the selected client and schedulespower delivery based on a predefined schedule referred to here as BeaconBeat Schedule (“BBS”).

As discussed above, communication is first established between thewireless power delivery system (“charger”) and the various powerreceiver clients #1-#N in a wireless power delivery environment. Thewireless power delivery system then generates transmission schedulinginformation which can include beacon scheduling information and powerscheduling information. The beacon scheduling information can include a“Beacon Beat Schedule.” The BBS cycle schedules and organizes powerdelivery/beacon broadcasting between the charger and the clients in theenvironment. As discussed herein, generation of the transmissionschedule can include selection of devices if there are more than athreshold number of devices (e.g., thirty) in the wireless powerdelivery environment. Additionally, one or more devices can be placed ona “waitlist.”

Once the transmissions scheduling information is generated, the wirelesspower delivery system provides the transmission scheduling informationand a transmission code, e.g., a pseudorandom sequence to the powerreceiver clients in the wireless power delivery environment. In someembodiments, only relevant scheduling information (e.g., scheduling orassignment information for a particular power receiver client) may beprovided to the particular power receiver client. Alternatively, all orjust portions of the scheduling information may be provided to the powerreceiver clients.

Since only one unique pseudorandom sequence is used by the wirelesspower delivery system in the example of FIG. 6, the wireless powerdelivery system schedules every client, e.g., #1-#N to broadcast itsencoded beacon (e.g., phase modulated) at different times. This scheduleguarantees power delivery for the clients. However, when many clients(e.g., thirty or more) have to share a limited number of cycles persecond (e.g., one hundred cycles per second), the clients may end upwith limited beacons each second (approximately three beacons for thirtyclients in a system with one hundred cycles per second). The limitedcycles can potentially limit the amount of wireless power the devicesreceive by leaving the power receiver clients out of their powerdelivery focus for relatively long periods of time. Moreover, trackingmovement of the client with fewer beacons per second can result inpotentially “locking” onto an unauthorized source the granularity of amoving device decreased. It is appreciated that each system may havemore or fewer than one hundred cycles per second.

FIG. 7 is another signaling diagram illustrating example transmissionschedule 700 for multiple power receiver clients #1-N and a wirelesspower delivery system in a wireless power delivery environment,according to some embodiment. The example transmission schedule 700involves use of a multiple pseudorandom sequences. Although a singlecharger is shown in the example of FIG. 7, it is appreciated that thewireless power delivery environment can include multiple wireless powerreceiver clients.

The example of FIG. 7 is similar to the example of FIG. 6 except thatthe wireless power delivery system, e.g., charger issues and/orotherwise assigns a different transmission code e.g., pseudorandomsequence, to each client for use as their beacon encoding scheme alongwith its scheduled slot to broadcast the modulated beacon.Advantageously, when unique transmission codes are used for each client,the beacon transmission schedule can direct the clients to transmittheir encoded beacons simultaneously or near simultaneously. This schemecan increase quantity of the beacons that the devices send to thecharger per second which decreases the likelihood that the chargerinadvertently locks on to an unauthorized source

The client broadcasts the encode beacon, e.g., phase-modulated beacon,utilizing the provided transmission code (pseudorandom sequence). Thewireless power delivery system, e.g., charger, detects the phasemodulated beacons based on the assigned transmission code (e.g.,pseudorandom sequence) and schedules power delivery based on apredefined power schedule which can also be provided to clients asdiscussed herein. In this example, the charger has a phase detectionmode before each power cycle. As shown, the phase detection mode (alsoreferred to as an encoded beacon detection mode) can be divided intochunks corresponding to each client. Alternatively, in some embodiments,the phases can be detected simultaneously by the charger.

In some embodiments, the examples described herein assume accurate timeclock alignment approaching accuracy in the range of 1-in-a-billionaccuracy or a 1 part per billion (ppb) variation. In some embodiments,the power receiving clients can therefor adjust internal clocks to alignwith the power delivery cycle of the charger for efficient powerdelivery. Alternatively or additionally, since the clients send tones(as part of beacon signal) for a known duration and at an expected rate,the charger can determine if a client's clock is fast or slow bymeasuring the actual tone signal received. The charger can then send anadjustment value for the client to apply to its system clock.

In the examples discussed herein the embodiments can include a datacommunication module, which can be used to coordinate events.Additionally, in some embodiments the beacon signal, which is primarilyreferred to herein as a continuous waveform, can alternatively oradditionally take the form of a modulated signal.

FIG. 8 depicts a block diagram illustrating example components of arepresentative mobile device or tablet computer 800 with a wirelesspower receiver or client in the form of a mobile (or smart) phone ortablet computer device, according to an embodiment. Various interfacesand modules are shown with reference to FIG. 8, however, the mobiledevice or tablet computer does not require all of modules or functionsfor performing the functionality described herein. It is appreciatedthat, in many embodiments, various components are not included and/ornecessary for operation of the category controller. For example,components such as GPS radios, cellular radios, and accelerometers maynot be included in the controllers to reduce costs and/or complexity.Additionally, components such as ZigBee radios and RFID transceivers,along with antennas, can populate the Printed Circuit Board.

The wireless power receiver client can be a power receiver clients 103of FIG. 1, although alternative configurations are possible.Additionally, the wireless power receiver client can include one or moreRF antennas for reception of power and/or data signals from a charger,e.g., charger 101 of FIG. 1.

FIG. 9 depicts a diagrammatic representation of a machine, in theexample form, of a computer system within which a set of instructions,for causing the machine to perform any one or more of the methodologiesdiscussed herein, may be executed.

In the example of FIG. 9, the computer system includes a processor,memory, non-volatile memory, and an interface device. Various commoncomponents (e.g., cache memory) are omitted for illustrative simplicity.The computer system 900 is intended to illustrate a hardware device onwhich any of the components depicted in the example of FIG. 1 (and anyother components described in this specification) can be implemented.For example, the computer system can be any radiating object or antennaarray system. The computer system can be of any applicable known orconvenient type. The components of the computer system can be coupledtogether via a bus or through some other known or convenient device.

The processor may be, for example, a conventional microprocessor such asan Intel Pentium microprocessor or Motorola power PC microprocessor. Oneof skill in the relevant art will recognize that the terms“machine-readable (storage) medium” or “computer-readable (storage)medium” include any type of device that is accessible by the processor.

The memory is coupled to the processor by, for example, a bus. Thememory can include, by way of example but not limitation, random accessmemory (RAM), such as dynamic RAM (DRAM) and static RAM (SRAM). Thememory can be local, remote, or distributed.

The bus also couples the processor to the non-volatile memory and driveunit. The non-volatile memory is often a magnetic floppy or hard disk, amagnetic-optical disk, an optical disk, a read-only memory (ROM), suchas a CD-ROM, EPROM, or EEPROM, a magnetic or optical card, or anotherform of storage for large amounts of data. Some of this data is oftenwritten, by a direct memory access process, into memory during executionof software in the computer 900. The non-volatile storage can be local,remote, or distributed. The non-volatile memory is optional becausesystems can be created with all applicable data available in memory. Atypical computer system will usually include at least a processor,memory, and a device (e.g., a bus) coupling the memory to the processor.

Software is typically stored in the non-volatile memory and/or the driveunit. Indeed, for large programs, it may not even be possible to storethe entire program in the memory. Nevertheless, it should be understoodthat for software to run, if necessary, it is moved to a computerreadable location appropriate for processing, and for illustrativepurposes, that location is referred to as the memory in this paper. Evenwhen software is moved to the memory for execution, the processor willtypically make use of hardware registers to store values associated withthe software, and local cache that, ideally, serves to speed upexecution. As used herein, a software program is assumed to be stored atany known or convenient location (from non-volatile storage to hardwareregisters) when the software program is referred to as “implemented in acomputer-readable medium”. A processor is considered to be “configuredto execute a program” when at least one value associated with theprogram is stored in a register readable by the processor.

The bus also couples the processor to the network interface device. Theinterface can include one or more of a modem or network interface. Itwill be appreciated that a modem or network interface can be consideredto be part of the computer system. The interface can include an analogmodem, isdn modem, cable modem, token ring interface, satellitetransmission interface (e.g. “direct PC”), or other interfaces forcoupling a computer system to other computer systems. The interface caninclude one or more input and/or output devices. The I/O devices caninclude, by way of example but not limitation, a keyboard, a mouse orother pointing device, disk drives, printers, a scanner, and other inputand/or output devices, including a display device. The display devicecan include, by way of example but not limitation, a cathode ray tube(CRT), liquid crystal display (LCD), or some other applicable known orconvenient display device. For simplicity, it is assumed thatcontrollers of any devices not depicted in the example of FIG. 9 residein the interface.

In operation, the computer system 900 can be controlled by operatingsystem software that includes a file management system, such as a diskoperating system. One example of operating system software withassociated file management system software is the family of operatingsystems known as Windows® from Microsoft Corporation of Redmond, Wash.,and their associated file management systems. Another example ofoperating system software with its associated file management systemsoftware is the Linux operating system and its associated filemanagement system. The file management system is typically stored in thenon-volatile memory and/or drive unit and causes the processor toexecute the various acts required by the operating system to input andoutput data and to store data in the memory, including storing files onthe non-volatile memory and/or drive unit.

Some portions of the detailed description may be presented in terms ofalgorithms and symbolic representations of operations on data bitswithin a computer memory. These algorithmic descriptions andrepresentations are the means used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm is here, and generally,conceived to be a self-consistent sequence of operations leading to adesired result. The operations are those requiring physicalmanipulations of physical quantities. Usually, though not necessarily,these quantities take the form of electrical or magnetic signals capableof being stored, transferred, combined, compared, and otherwisemanipulated. It has proven convenient at times, principally for reasonsof common usage, to refer to these signals as bits, values, elements,symbols, characters, terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise, as apparent from the followingdiscussion, it is appreciated that throughout the description,discussions utilizing terms such as “processing” or “computing” or“calculating” or “determining” or “displaying” or the like, refer to theaction and processes of a computer system, or similar electroniccomputing device, that manipulates and transforms data represented asphysical (electronic) quantities within the computer system's registersand memories into other data similarly represented as physicalquantities within the computer system memories or registers or othersuch information storage, transmission or display devices.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus. Various general purposesystems may be used with programs in accordance with the teachingsherein, or it may prove convenient to construct more specializedapparatus to perform the methods of some embodiments. The requiredstructure for a variety of these systems will appear from thedescription below. In addition, the techniques are not described withreference to any particular programming language, and variousembodiments may thus be implemented using a variety of programminglanguages.

In alternative embodiments, the machine operates as a standalone deviceor may be connected (e.g., networked) to other machines. In a networkeddeployment, the machine may operate in the capacity of a server or aclient machine in a client-server network environment or as a peermachine in a peer-to-peer (or distributed) network environment.

The machine may be a server computer, a client computer, a personalcomputer (PC), a tablet PC, a laptop computer, a set-top box (STB), apersonal digital assistant (PDA), a cellular telephone, an iPhone, aBlackberry, a processor, a telephone, a web appliance, a network router,switch or bridge, or any machine capable of executing a set ofinstructions (sequential or otherwise) that specify actions to be takenby that machine.

While the machine-readable medium or machine-readable storage medium isshown in an exemplary embodiment to be a single medium, the term“machine-readable medium” and “machine-readable storage medium” shouldbe taken to include a single medium or multiple media (e.g., acentralized or distributed database, and/or associated caches andservers) that store the one or more sets of instructions. The term“machine-readable medium” and “machine-readable storage medium” shallalso be taken to include any medium that is capable of storing, encodingor carrying a set of instructions for execution by the machine and thatcause the machine to perform any one or more of the methodologies of thepresently disclosed technique and innovation.

In general, the routines executed to implement the embodiments of thedisclosure, may be implemented as part of an operating system or aspecific application, component, program, object, module or sequence ofinstructions referred to as “computer programs.” The computer programstypically comprise one or more instructions set at various times invarious memory and storage devices in a computer, and that, when readand executed by one or more processing units or processors in acomputer, cause the computer to perform operations to execute elementsinvolving the various aspects of the disclosure.

Moreover, while embodiments have been described in the context of fullyfunctioning computers and computer systems, those skilled in the artwill appreciate that the various embodiments are capable of beingdistributed as a program product in a variety of forms, and that thedisclosure applies equally regardless of the particular type of machineor computer-readable media used to actually effect the distribution.

Further examples of machine-readable storage media, machine-readablemedia, or computer-readable (storage) media include but are not limitedto recordable type media such as volatile and non-volatile memorydevices, floppy and other removable disks, hard disk drives, opticaldisks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital VersatileDisks, (DVDs), etc.), among others, and transmission type media such asdigital and analog communication links.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense, as opposed to anexclusive or exhaustive sense; that is to say, in the sense of“including, but not limited to.” As used herein, the terms “connected,”“coupled,” or any variant thereof, means any connection or coupling,either direct or indirect, between two or more elements; the coupling ofconnection between the elements can be physical, logical, or acombination thereof. Additionally, the words “herein,” “above,” “below,”and words of similar import, when used in this application, shall referto this application as a whole and not to any particular portions ofthis application. Where the context permits, words in the above DetailedDescription using the singular or plural number may also include theplural or singular number respectively. The word “or,” in reference to alist of two or more items, covers all of the following interpretationsof the word: any of the items in the list, all of the items in the list,and any combination of the items in the list.

The above detailed description of embodiments of the disclosure is notintended to be exhaustive or to limit the teachings to the precise formdisclosed above. While specific embodiments of, and examples for, thedisclosure are described above for illustrative purposes, variousequivalent modifications are possible within the scope of thedisclosure, as those skilled in the relevant art will recognize. Forexample, while processes or blocks are presented in a given order,alternative embodiments may perform routines having steps, or employsystems having blocks, in a different order, and some processes orblocks may be deleted, moved, added, subdivided, combined, and/ormodified to provide alternative or subcombinations. Each of theseprocesses or blocks may be implemented in a variety of different ways.Also, while processes or blocks are, at times, shown as being performedin a series, these processes or blocks may instead be performed inparallel, or may be performed at different times. Further, any specificnumbers noted herein are only examples: alternative implementations mayemploy differing values or ranges.

The teachings of the disclosure provided herein can be applied to othersystems, not necessarily the system described above. The elements andacts of the various embodiments described above can be combined toprovide further embodiments.

Any patents and applications and other references noted above, includingany that may be listed in accompanying filing papers, are incorporatedherein by reference. Aspects of the disclosure can be modified, ifnecessary, to employ the systems, functions, and concepts of the variousreferences described above to provide yet further embodiments of thedisclosure.

These and other changes can be made to the disclosure in light of theabove Detailed Description. While the above description describescertain embodiments of the disclosure, and describes the best modecontemplated, no matter how detailed the above appears in text, theteachings can be practiced in many ways. Details of the system may varyconsiderably in its implementation details, while still beingencompassed by the subject matter disclosed herein. As noted above,particular terminology used when describing certain features or aspectsof the disclosure should not be taken to imply that the terminology isbeing redefined herein to be restricted to any specific characteristics,features, or aspects of the disclosure with which that terminology isassociated. In general, the terms used in the following claims shouldnot be construed to limit the disclosure to the specific embodimentsdisclosed in the specification, unless the above Detailed Descriptionsection explicitly defines such terms. Accordingly, the actual scope ofthe disclosure encompasses not only the disclosed embodiments, but alsoall equivalent ways of practicing or implementing the disclosure underthe claims.

While certain aspects of the disclosure are presented below in certainclaim forms, the inventors contemplate the various aspects of thedisclosure in any number of claim forms. For example, while only oneaspect of the disclosure is recited as a means-plus-function claim under35 U.S.C. §112, ¶6, other aspects may likewise be embodied as ameans-plus-function claim, or in other forms, such as being embodied ina computer-readable medium. (Any claims intended to be treated under 35U.S.C. §112, ¶6 will begin with the words “means for”.) Accordingly, theapplicant reserves the right to add additional claims after filing theapplication to pursue such additional claim forms for other aspects ofthe disclosure.

The detailed description provided herein may be applied to othersystems, not necessarily only the system described above. The elementsand acts of the various examples described above can be combined toprovide further implementations of the invention. Some alternativeimplementations of the invention may include not only additionalelements to those implementations noted above, but also may includefewer elements. These and other changes can be made to the invention inlight of the above Detailed Description. While the above descriptiondefines certain examples of the invention, and describes the best modecontemplated, no matter how detailed the above appears in text, theinvention can be practiced in many ways. Details of the system may varyconsiderably in its specific implementation, while still beingencompassed by the invention disclosed herein. As noted above,particular terminology used when describing certain features or aspectsof the invention should not be taken to imply that the terminology isbeing redefined herein to be restricted to any specific characteristics,features, or aspects of the invention with which that terminology isassociated. In general, the terms used in the following claims shouldnot be construed to limit the invention to the specific examplesdisclosed in the specification, unless the above Detailed Descriptionsection explicitly defines such terms. Accordingly, the actual scope ofthe invention encompasses not only the disclosed examples, but also allequivalent ways of practicing or implementing the invention.

What is claimed is:
 1. A wireless power delivery system comprising:multiple antennas; control circuitry operatively coupled to the multipleantennas, the control circuitry configured to: establish a wirelesscommunications link with client devices in a wireless power deliveryenvironment via one or more of the multiple antennas; processclient-specific information received from the wireless devices to selecta set of the client devices for power reception in the wireless powerdelivery environment and generate beacon transmission schedulinginformation, wherein the beacon transmission scheduling informationincludes beacon transmission scheduling assignments for the selected setof client devices; and direct the one or more antennas to send a beacontransmission scheduling assignment and a transmission code to each ofthe selected set of client devices, wherein the transmission code isused to isolate signals transmitted from the selected set of clientdevices.
 2. The wireless power delivery system of claim 1, wherein thecontrol circuitry is further configured to select a unique transmissioncode for each device of the selected set of client devices.
 3. Thewireless power delivery system of claim 2, wherein the transmission codeis unique to the wireless power delivery system.
 4. The wireless powerdelivery system of claim 1, wherein the transmission code comprises apseudo-random sequence.
 5. The wireless power delivery system of claim1, wherein the control circuitry is further configured to: decode acoded beacon signal received from a particular client device todetermine whether the particular client device is an authorized device,wherein authorized devices are included in the selected set of clientdevices.
 6. The wireless power delivery system of claim 5, wherein thecoded beacon signal is phase-modulated based on the transmission code.7. The wireless power delivery system of claim 6, wherein the controlcircuitry is further configured to: measure phases at which the codedbeacon signal is received at one or more of the multiple antennas,wherein one or more of the multiple antennas are radio frequencyadaptively-phased antennas configurable to direct wireless power toindividual client devices in the wireless power delivery environment;determine or update location information corresponding to the clientdevice based on the measured phases; and adjust the adaptively-phasedantennas to direct wireless power to the particular client.
 8. Thewireless power delivery system of claim 1, wherein the control circuitryis further configured to: process the client-specific informationreceived from the wireless devices to generate power transmissionscheduling information; and direct the one or more antennas to send thepower transmission scheduling information to the selected set of clientdevices.
 9. The wireless power delivery system of claim 1, wherein thebeacon transmission scheduling information comprises a beacon beatschedule (BBS).
 10. The wireless power delivery system of claim 1,wherein the beacon transmission scheduling assignments overlap.
 11. Amethod of operating a power reception apparatus for wirelessly receivingpower from a wireless power delivery system in a wireless power deliveryenvironment, the method comprising: establishing a wirelesscommunications link with the wireless power delivery system;transmitting client-specific information to the wireless power deliverysystem; receiving a beacon transmission scheduling information and atransmission code from the a wireless power delivery system; encoding abeacon signal with the transmission code resulting in an encoded beaconsignal; and sending the encoded beacon signal to the wireless powerdelivery system during a beacon transmission assignment, wherein thebeacon transmission assignment is indicated by the beacon transmissionscheduling information.
 12. The method of claim 11, wherein thetransmission code comprises a pseudo-random sequence, and whereinencoding the beacon signal comprises one or more of phase shifting thebeacon signal based on the pseudo-random sequence, or modulating thebeacon signal based on the pseudo-random sequence.
 13. The method ofclaim 12, wherein encoding the beacon signal comprises phase shiftingthe beacon signal based on the pseudo-random sequence, and wherein thepseudo-random sequence comprises a binary number where each “1” of thebinary number indicates a predetermined amount of phase shift and each“0” indicates zero phase shift.
 14. The method of claim 1, furthercomprising: in response to sending the encoded beacon signal, receivingwireless power from the wireless power delivery system during a powercycle assigned to the power reception apparatus.
 15. The method of claim11, wherein the client-specific information includes system informationspecific to a wireless device in which the power reception apparatus isembedded.
 16. The method of claim 11, wherein the client-specificinformation includes one or more of a battery level of a wireless devicein which the power reception apparatus is embedded, battery usageinformation of the wireless device, a battery level of the powerreception apparatus, battery usage information of the power receptionapparatus, information regarding a previous charge cycle, informationregarding a previous charge time, information regarding a previouscharger that provided power to the wireless device, priority charginginformation, received signal strength indication (RSSI) information,temperature information of the wireless device, or temperatureinformation of the power reception apparatus.
 17. A method of operatinga wireless power delivery system for providing isolated wireless powerdelivery to wireless devices in a wireless power delivery environment,the method comprising: establishing a wireless communications link withthe client devices in the wireless power delivery environment; receivingclient-specific information from the wireless devices; selecting a setof the client devices for power reception in the wireless power deliveryenvironment and generating beacon transmission scheduling informationbased, at least in part, on the client-specific information, wherein thebeacon transmission scheduling information includes beacon transmissionscheduling assignments for the selected set of client devices; andsending a beacon transmission scheduling assignment and a transmissioncode to each of the selected set of client devices, wherein thetransmission code is used to isolate signaling transmitted from theselected set of client devices.
 18. The method of claim 17, wherein thewireless power delivery system uses a unique transmission code for eachclient of the set of the selected set of client devices.
 19. The methodof claim 17, wherein the transmission code comprises a pseudo-randomsequence, the method further comprising: decoding an encoded beaconsignal received from a particular client device to determine whether theparticular client device is an authorized device, wherein authorizeddevices are included in the selected set of client devices and assigneda unique transmission code.
 20. The method of claim 17, furthercomprising: measuring phases at which the coded beacon signal isreceived at one or more of the multiple antennas, wherein one or more ofthe multiple antennas are radio frequency adaptively-phased antennasconfigurable to direct wireless power to individual client devices inthe wireless power delivery environment; determining or updatinglocation information corresponding to the client device based on themeasured phases; and directing wireless power to the particular client.